| Original author(s) | Robert McCool |
|---|---|
| Developer(s) | Apache Software Foundation |
| Initial release | 1995[1] |
| Stable release | 2.2.21 / September 13, 2011 |
| Preview release | 2.3.16-beta / December 20, 2011 |
| Written in | C |
| Operating system | Cross-platform |
| Available in | English |
| Type | Web server |
| License | Apache License 2.0 |
| Website | httpd.apache.org |
The Apache HTTP Server, commonly referred to as Apache (/əˈpætʃiː/), is web server software notable for playing a key role in the initial growth of the World Wide Web.[2] In 2009 it became the first web server software to surpass the 100 million website milestone.[3] Apache was the first viable alternative to the Netscape Communications Corporation web server (currently named Oracle iPlanet Web Server), and since has evolved to rival other web servers in terms of functionality and performance. Typically Apache is run on a Unix-like operating system.[4]
Apache is developed and maintained by an open community of developers under the auspices of the Apache Software Foundation. The application is available for a wide variety of operating systems, including Unix, FreeBSD, Linux, Solaris, Novell NetWare, AmigaOS, Mac OS X, Microsoft Windows, OS/2, TPF, and eComStation. Released under the Apache License, Apache is open-source software.
Apache was originally based on NCSA HTTPd code. The NCSA code has since been removed from Apache, due to a rewrite.
Since April 1996 Apache has been the most popular HTTP server software in use. As of May 2011[update] Apache was estimated to serve 63% of all websites and 66% of the million busiest.[5]
Contents |
According to the FAQ in the Apache project website, the name Apache was chosen out of respect to the Native American tribe Apache (Inde) and its superior skills in warfare and strategy. The website also explains the popular but erroneous origin of the name, A Patchy Server (since it was a conjunction of software patches)[6]
Apache supports a variety of features, many implemented as compiled modules which extend the core functionality. These can range from server-side programming language support to authentication schemes. Some common language interfaces support Perl, Python, Tcl, and PHP. Popular authentication modules include mod_access, mod_auth, mod_digest, and mod_auth_digest, the successor to mod_digest. A sample of other features include Secure Sockets Layer and Transport Layer Security support (mod_ssl), a proxy module (mod_proxy), a URL rewriter (also known as a rewrite engine, implemented under mod_rewrite), custom log files (mod_log_config), and filtering support (mod_include and mod_ext_filter).
Popular compression methods on Apache include the external extension module, mod_gzip, implemented to help with reduction of the size (weight) of web pages served over HTTP. ModSecurity is an open source intrusion detection and prevention engine for web applications. Apache logs can be analyzed through a web browser using free scripts such as AWStats/W3Perl or Visitors.
Virtual hosting allows one Apache installation to serve many different actual websites. For example, one machine with one Apache installation could simultaneously serve www.example.com, www.example.org, test47.test-server.example.edu, etc.
Apache features configurable error messages, DBMS-based authentication databases, and content negotiation. It is also supported by several graphical user interfaces (GUIs).
It supports password authentication and digital certificate authentication. Apache has a built in search engine and an HTML authorizing tool and supports FTP.
Although the main design goal of Apache is not to be the "fastest" web server, Apache does have performance comparable to other "high-performance" web servers. Instead of implementing a single architecture, Apache provides a variety of MultiProcessing Modules (MPMs) which allow Apache to run in a process-based, hybrid (process and thread) or event-hybrid mode, to better match the demands of each particular infrastructure. This implies that the choice of correct MPM and the correct configuration is important. Where compromises in performance need to be made, the design of Apache is to reduce latency and increase throughput, relative to simply handling more requests, thus ensuring consistent and reliable processing of requests within reasonable time-frames.
The Apache version considered by the Apache Foundation as providing high-performance is the multi-threaded version which mixes the use of several processes and several threads per process.[7]
While this architecture works faster than the previous multi-process based topology (because threads have a lower overhead than processes), it does not match the performances of the event-based architecture provided by other servers, especially when they process events with several worker threads.[8]
This difference can be easily explained by the overhead that one thread per connection brings (as opposed to a couple of worker threads per CPU, each processing many connection events). Each thread needs to maintain its own stack, environment, and switching from one thread to another is also an expensive task for CPUs.
With the release of Apache 2.0, the Apache Foundation changed its license. Some Apache users did not like the change and continued the use of pre-2.0 Apache versions (typically 1.3.x). The OpenBSD project went to the extent of effectively forking Apache 1.3.x for its purposes.[9]
|
|||||||||||||||||||||||||||||